System and method for tracking configuration changes in enterprise product

ABSTRACT

In one embodiment, an automatic, remote and centralized configuration management system for tracking configuration changes in an enterprise product is provided. The system comprises at least one subsystem forming a part of the enterprise product, an agent coupled to the subsystem, the agent configured for creating one or more configuration snapshots of the subsystem and a configuration manager operably coupled to the agent, the configuration manager configured to communicate with the agent to collect the one or more configuration snapshots so as to track the configuration changes in the enterprise product.

FIELD OF INVENTION

The invention generally relates to networked systems and more particularly to managing and troubleshooting devices within networks by tracking configuration changes through monitoring of configuration status of devices on the network.

BACKGROUND OF THE INVENTION

Managing and troubleshooting an enterprise product (which usually comprises a large number of loosely coupled systems) is very crucial and essential for the owner of the product. This emphasizes the need of having tools that aid in troubleshooting. Prior art systems do not provide a service engineer with a systematic way of troubleshooting problems. To arrive at a root cause of the problem, the service engineer may need to go through a number of log files, and manually check various states of the system. One of the main tasks that he does in this regard is to check the configuration of various components of the system and see if there are any changes. It is extremely cumbersome and time consuming to do this manually for enterprise failures. Hence there exists a need to simplify this process and automate it.

BRIEF DESCRIPTION OF THE INVENTION

The above-mentioned shortcomings, disadvantages and (problems are addressed herein which will be understood by reading and understanding the following specification.

In one embodiment, a method of tracking and auditing configuration changes in an enterprise product is provided. The method comprises steps of receiving a first trigger for creating a configuration snapshot, creating a first configuration snapshot in response to the received first trigger, the first configuration snapshot corresponding to a first time stamp, receiving a second trigger for creating a configuration snapshot, creating a second configuration snapshot in response to the received second trigger, the second configuration snapshot corresponding to a second time stamp, comparing the first and second configuration snapshots to track configuration changes in the enterprise product and displaying the tracked configuration changes.

In another embodiment, an automatic, remote and centralized configuration management system for tracking configuration changes in an enterprise product is provided. The system comprises at least one subsystem forming a part of the enterprise product, an agent coupled to the subsystem, the agent configured for creating one or more configuration snapshots of the subsystem and a configuration manager operably coupled to the agent, the configuration manager configured to communicate with the agent to collect the one or more configuration snapshots so as to track the configuration changes in the enterprise product.

Systems and methods of varying scope are described herein. In addition to the aspects and advantages described in this summary, further aspects and advantages will become apparent by reference to the drawings and with reference to the detailed description that follows.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a block diagram of a system for tracking configuration changes in an enterprise product as described in an embodiment; and

FIG. 2 shows a flow diagram depicting a method of tracking configuration changes in an enterprise product as described in an embodiment.

DETAILED DESCRIPTION OF THE INVENTION

In the following detailed description, reference is made to the accompanying drawings that form a part hereof, and in which is shown by way of illustration specific embodiments, which may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the embodiments, and it is to be understood that other embodiments may be utilized and that logical, mechanical, electrical and other changes may be made without departing from the scope of the embodiments. The following detailed description is, therefore, not to be taken in a limiting sense.

Turning now to FIG. 1, as described in one embodiment, an automatic, remote and centralized configuration management system 100 for tracking configuration changes in an enterprise product is provided. The system 100 comprises at least one subsystem 102 forming a part of the enterprise product and an agent 104 coupled to the subsystem 102, the agent 104 configured for creating one or more configuration snapshots of the subsystem 102. The system 100 further comprises a configuration manager 108 operably coupled to the agent 104, the configuration manager 108 configured to communicate with the agent 104 to collect the one or more configuration snapshots so as to track the configuration changes in the enterprise product.

The invention provides a mechanism to collect various configurations of an enterprise product and/or distributed system using multiple configuration agents 104 and 106 and create snapshots of these configurations out side the distributed system for example, in a serviceability database 112 located remotely from the enterprise product. Using such a mechanism, various user needs for configuration management such as viewing current and/or any of the previous configurations and comparing configurations are addressed.

In an agent based framework each of the subsystem 102 for which configuration needs to be collected comprises a configuration agent 104 that is capable of collecting the configuration of the subsystem 102. Accordingly, in one exemplary embodiment, the system 100 comprises a first agent 104 coupled to a first subsystem 102 and a second agent 106 coupled to a second subsystem 110. Skilled artisans shall however appreciate that the enterprise product can comprise any number of subsystems wherein each subsystem is coupled to an agent. The first agent 104 and the second agent 106 communicate with the configuration manager 108 through a standard interface.

In one embodiment, the first agent 104 and the second agent 106 communicate with the configuration manager 108 using industry standard communication protocols like JMX and/or web services.

Turning now to FIG. 2, in one embodiment, a method 200 of tracking configuration changes in an enterprise product is provided. The method 200 comprises steps of receiving a first trigger for creating a configuration snapshot at step 202, creating a first configuration snapshot in response to the received first trigger, the first configuration snapshot corresponding to a first time stamp at step 204, receiving a second trigger for creating a configuration snapshot at step 206, creating a second configuration snapshot in response to the received second trigger, the second configuration snapshot corresponding to a second time stamp at step 208, comparing the first and second configuration snapshots to track configuration changes in the enterprise product at step 210 and displaying the tracked configuration changes at step 212.

The method 200 further comprises storing the first and second configuration snapshots in a serviceability database 112 and retrieving the first and second configuration snapshots from the serviceability database 112. The configuration snapshots are stored outside the enterprise system in the serviceability database 112 located remotely from the enterprise product. This facilitates the review of configuration changes of the enterprise system when the enterprise system is not accessible due to failure.

With reference to FIG. 1, the system 100 further comprises a configuration management user interface 114 coupled to the configuration manager 108. The configuration manager 108 provides the necessary infrastructure for interaction between the configuration management user interface 114, agents 104 and 106 and serviceability database 112 for creating configuration snapshots, viewing and/or editing runtime configuration, and comparing configurations. In one embodiment, the configuration manager 108 and the configuration management user interface 114 may be deployed on a device storing the serviceability database 112.

The method 200 further comprises comparing the first and second configuration snapshots to track configuration changes in the enterprise product. Either of the first and second configuration snapshots may indicate the current configuration of the subsystem 102. Therefore, the system 100 provides a mechanism for the user to view the current configuration of the enterprise system and also any of the previous configuration snapshots collected. The user will have the ability to see a history of all the snapshots created with their metadata such as the time of creation, environment in which it is created.

The ability of the system 100 to provide comparison between two configuration snapshots facilitates troubleshooting. The user will have the ability to compare the current configuration to any of the configuration snapshots collected earlier or compare any of the two previously collected configuration snapshots. The differences in configurations are highlighted to the user.

In one embodiment, the enterprise product may be setup under multiple environments such as production, test and training. The system 100 is configured to manage system configuration across these multiple environments. The configurations can be collected from these different environments. The configuration management user interface 114 is configured to show the list of various configuration snapshots collected from different environments and also provides the ability to compare them. The differences in configuration between any two snapshots and/or between one of the configuration snapshots and the current configuration can be shown to the user. Only the differences and/or various properties can be seen with differences highlighted.

Comparing snapshots of configurations between different environments of the enterprise product is useful. Further, the system 100 is also configured to compare configurations within an environment, for example first application server vs second application server. Further in a clustered and/or load balanced setup the system 100 can be utilized to compare the configuration to two different devices (having similar or disjoint functions) within the cluster.

The method 200 further comprises generating an alert on tracking configuration changes in the enterprise product. For this purpose, the system 100 may comprise an alerting system to notify configured users of changes in system configuration. When anew snapshot is created, a check can be made to see if there are differences in configuration, Following the detection of changes, the configured users for various components can be notified of the change in configuration. The system 100 can be configured to provide support for an escalation hierarchy. Further, knowledge base of resolutions keeps track of who provided the resolution earlier in order to simplify and fasten the resolution process.

The creation of configuration snapshots is based on a trigger. The trigger generated is one of a scheduled, manual and event based trigger. The system 100 is configured to schedule creation of configuration snapshots on a periodic basis. The system 100 can further be configured to compare the current configuration with the previous configuration snapshot prior to creating a successive configuration snapshot. Alternatively, the system 100 may be configured to trigger the snapshot creation following the occurrence of an event. Further, the system 100 may be manually triggered to create a configuration snapshot. Example of event based agents can monitor one or more events and can subsequently trigger the configuration snapshot collection process.

In another embodiment, the agent 104 has the capability to trigger partial configuration collection. If a particular agent 104 detects a change in configuration it can collect the configuration and send it to the configuration manager 108.

Each configuration snapshot comprises one or more configuration values. The configuration values comprise one of static and dynamic configuration values. Example of static configurations would be the properties files that contain configurations. Examples of dynamic configurations are Linux Environment Variables.

The method 200 further comprises steps of determining the validity of the configuration values and generating a notification upon determining the invalidity of the configuration values. The system 100 is configured to validate configurations following collection of each configuration snapshot and notify and/or alert if a certain configuration is not valid. In this regard, the system 100 is configured to create validation rules for different types of configurations. For example, if a database URL is desired to have a predetermined pattern and assuming there is a change in configuration snapshots obtained at different time stamps in which the configuration value corresponding to the configuration snapshot obtained at one of the time stamps is invalid, then following the creation of the configuration snapshot, which is taker determined to be invalid, a validation check is made and an alert is generated. This will help in proactive troubleshooting of issues.

The method 200 further comprises collecting audit information about the configuration snapshot. The system 100 is configured to collect the audit information of various configuration changes. In one exemplary embodiment, the agents 104 and 106 for various subsystem 102 and 110 are adapted to read the log files for identifying audit information of configuration changes and send the audit information along with the configuration snapshots to the configuration manager 108. This provides an improved mechanism to manage the configurations whereby the documentation of who made changes and when is carried out.

In one embodiment, whenever a new system is delivered to the user in the process of providing upgrades to the system, the user needs to configure the system. The system 100 described herein provides configuration tools that aid the user in this process and the user is presented with configuration forms for filling details. The configuration snapshots can be used to partially fill the forms against defaults and previously set configurations. This simplifies the upgradation process.

The method 200 described herein provides a means to simplify the task of tracking configuration changes in an enterprise system using an agent based framework. When configuration is modified and needs to be applied on to the target enterprise system, the framework uses the agents 104 and 106 to apply these changes on to various subsystems 102 and 110.

The main advantage of agent based system is that it can be leveraged to use the most convenient way to collect the configuration of the subsystem. Each of the subsystem may use a different type of agent. Ex: Database, Linux may each require a different type of agent. It provides language independence to the agent as long as it can be accessed using one of the standard communication protocols. Such a framework can be extended to collect the configuration of the legacy products, which are developed using legacy programming languages such as C, VB. Further, the agents can also be employed to collect third party component's configuration.

With such a system, the process of configuration management is automated and can be performed from a remote location using web-based tools. The system setup configuration tool is a web-based tool that can be launched from any remote location using a URL. The service engineer need not access the enterprise system and read through the various configuration files to look for changes, rather it can be done through a web console and the whole process is automatic. This process is also centralized that the configurations of the various subsystems can be managed from a single location.

Further, the system comprises an integrated workflow management and alerting system. When a configuration is modified, it will automatically trigger the corresponding workflows for the configuration changes to take effect.

In various embodiments of the invention, a system and method for tracking configuration changes in an enterprise product are described. However, the embodiments are not limited and may be implemented in connection with different applications. The application of the invention can be extended to other areas, for example networked devices. The design can be carried further and implemented in various forms and specifications.

This written description uses examples to describe the subject matter herein, including the best mode, and also to enable any person skilled in the art to make and use the subject matter. The patentable scope of the subject matter is defined by the claims, and may include other examples that occur to those skilled in the art. Such other examples are intended to be within the scope of the claims if they have structural elements that do not differ from the literal language of the claims, or if they include equivalent structural elements with insubstantial differences from the literal language of the claims. 

1. A method of tracking configuration changes in an enterprise product, the method comprising: receiving a first trigger for creating a configuration snapshot; creating a first configuration snapshot in response to the received first trigger, the first configuration snapshot corresponding to a first time stamp; receiving a second trigger for creating a configuration snapshot, creating a second configuration snapshot in response to the received second trigger, the second configuration snapshot corresponding to a second time stamp; comparing the first and second configuration snapshots to track configuration changes in the enterprise product; and displaying the tracked configuration changes.
 2. The method of claim 1, further comprising generating an alert on tracking configuration changes in the enterprise product.
 3. The method of claim 1, further comprising: storing the first and second configuration snapshots in a serviceability database; and retrieving the first and second configuration snapshots from the serviceability database.
 4. The method of claim 1, wherein each configuration snapshot comprises one or more configuration values.
 5. The method of claim 4, further comprising: determining the validity of the configuration values; and generating a notification upon determining invalidity of the configuration values.
 6. The method of claim 5, wherein the configuration values comprise at least one of static and dynamic configuration values.
 7. The method of claim 1, further comprising collecting audit information about the configuration snapshot.
 8. The method of claim 1, wherein the serviceability database is located remotely from the enterprise product.
 9. The system of claim 1, Wherein the trigger generated is one of a scheduled, manual and event based trigger.
 10. An automatic, remote and centralized configuration management system for tracking configuration changes in an enterprise product, the system comprising: at least one subsystem forming a part of the enterprise product; an agent coupled to the subsystem, the agent configured for creating one or more configuration snapshots of the subsystem; and a configuration manager operably coupled to the agent, the configuration manager configured to communicate with the agent to collect the one or more configuration snapshots so as to track the configuration changes in the enterprise product.
 11. The system of claim 10, wherein a first agent is coupled to a first subsystem and a second agent is coupled to a second subsystem and wherein the first agent and the second agent communicate with the configuration manager through a standard interface.
 12. The system of claim 11, wherein the first agent and the second agent communicate with the configuration manager using communication protocols comprising JMX and web services.
 13. The system of claim 10, wherein the configuration manager is further configured for storing the first and second configuration snapshots in a serviceability database.
 14. The system of claim 10, wherein the enterprise product is set up in one of environments comprising production, test and training.
 15. The system of claim 10, further comprising a configuration management user interface coupled to the configuration manager. 